The ORPC migration PR (#763) inadvertently deleted the auto-compaction
trigger logic when sending messages. This restores:

- Check if usage >= threshold before sending regular messages
- Execute compaction with continueMessage instead of direct send
- Show 'Context threshold reached - auto-compacting...' toast
- Proper error handling with input/image restoration

The supporting infrastructure (checkAutoCompaction, CompactionWarning,
settings UI) remained intact - only the trigger logic was missing.

_Generated with `mux`_

Reverts:
- 470e4eb perf: fix streaming content delay from ORPC schema validation (#774)
- b437977 feat: add backend support for soft-interrupts (#767)
- df30cbc fix: use ResultSchema for sendMessage output to prevent field stripping (#773)
- 41c77ef fix: testUtils formatting (#771)
- 3ee7288 refactor: migrate IPC layer to ORPC for type-safe RPC (#763)

Reverts:
- 470e4eb perf: fix streaming content delay from ORPC schema validation
(#774)
- b437977 feat: add backend support for soft-interrupts (#767)
- df30cbc fix: use ResultSchema for sendMessage output to prevent field
stripping (#773)
- 41c77ef fix: testUtils formatting (#771)
- 3ee7288 refactor: migrate IPC layer to ORPC for type-safe RPC (#763)

Due to a huge number of regressions.

_Generated with `mux`_

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

fix: add @babel/preset-react for JSX transpilation in Jest tests

fix: add missing timestamp field to ToolCallEndEvent schema and usages

fix: use ref for ORPCProvider cleanup to avoid stale closure

The useEffect cleanup captured state at mount time ('connecting'),
so even after transitioning to 'connected', cleanup never ran.
Now stores cleanup function in a ref that's always current.

test: add feature branch to storybook mock branch list

Extend listBranches mock response with a feature branch example
to better represent realistic branch listings during component
development and testing.

fix: batch async message yields to prevent scroll issues

The oRPC async generator was yielding messages one at a time with async
boundaries, causing premature React renders during history replay. This
led to scroll-to-bottom firing before all messages loaded.

Extract createAsyncMessageQueue utility that yields all queued messages
synchronously (no async pauses within a batch). Used by both the real
router and storybook mocks to match original IPC callback behavior.

fix: add missing type discriminators to storybook chat messages

The MarkdownTables story was emitting messages without the required
`type: "message"` field. The `as WorkspaceChatMessage` type casts
hid this from TypeScript, causing messages to not be recognized
by the chat processor and rendering "No Messages Yet" instead.

Also fix ChatEventProcessor tests that had invalid event shapes:
- Remove invalid `role`/`timestamp` from stream-start events
- Add missing `workspaceId`/`tokens` to delta events

fix: use useLayoutEffect for initial scroll to fix Chromatic snapshots

The scroll-to-bottom when workspace loads was using useEffect with
requestAnimationFrame, which runs asynchronously after browser paint.
Chromatic could capture the snapshot before scroll completed.

Switch to useLayoutEffect which runs synchronously after DOM mutations
but before paint, ensuring scroll happens before Chromatic captures.
This also removes the need for the RAF wrapper since useLayoutEffect
already guarantees DOM is ready.

fix: add play functions to ensure Chromatic captures scrolled state

- Add waitForChatScroll play function that waits for messages to load
  and scroll to complete before Chromatic takes screenshots
- Add data-testid="message-window" to scroll container in AIView
- Add data-testid="chat-message" to message wrappers for test queries
- Apply play function to ActiveWorkspaceWithChat and MarkdownTables stories
- Fix ProviderIcon lint error: remove redundant "mux-gateway" union type
  (already included in ProviderName)

fix: resolve React Native typecheck errors

- Add missing 'error' event handler in normalizeChatEvent.ts
  Converts error events to stream-error for mobile display
- Fix result.metadata access in WorkspaceScreen.tsx
  ResultSchema wraps data, so access result.data.metadata not result.metadata
- Add RequestInitWithDispatcher type in aiService.ts
  Extends RequestInit with undici-specific dispatcher property for Node.js

fix: use queueMicrotask instead of setTimeout in story mocks

Replace setTimeout(..., 100) with queueMicrotask() for message delivery
in Storybook mocks. This ensures messages arrive synchronously (in the
microtask queue) rather than 100ms later, eliminating timing races with
Chromatic's screenshot capture.

- All onChat mock callbacks now use queueMicrotask for message delivery
- Add chromatic: { delay: 500 } as backup for ActiveWorkspaceWithChat
  and MarkdownTables stories
- Fix import: use storybook/test instead of @storybook/test (Storybook 10)

fix: remove deprecated @storybook/addon-interactions from config

In Storybook 10, interaction testing is built into the core and the
addon-interactions package was deprecated. Remove it from the addons
list to fix build failures caused by version mismatch.

fix: add semver 7.x to fix storybook build in CI

Storybook 10 imports semver/functions/sort.js which only exists in
semver 7.x. The root-level semver was 6.x (needed by babel), causing
ESM resolution in Node 20.x to fail in CI.

Adding semver ^7.x as a direct dependency forces the root-level
version to 7.x, which is backwards compatible with 6.x consumers.

fix: add missing fields to oRPC provider and workspace schemas

The ProviderConfigInfoSchema was missing couponCodeSet (for Mux Gateway)
and aws (for Bedrock). oRPC strips fields not in the schema, so these
values were never reaching the frontend UI.

Also fixes workspace.fork to use FrontendWorkspaceMetadataSchema instead
of WorkspaceMetadataSchema, ensuring namedWorkspacePath is not stripped.

refactor: consolidate provider types to single source of truth

Eliminates triple-definition of ProviderConfigInfo/AWSCredentialStatus types
that existed in providerService.ts, Settings/types.ts, and the oRPC schema.
Now the Zod schema is the single source of truth, with TypeScript types
derived via z.infer.

Adds conformance tests that validate oRPC schemas preserve all fields when
parsing - this would have caught the missing couponCodeSet/aws fields bug.

refactor: improve tool part schema type safety and remove dead code

1. Refactor MuxToolPartSchema using extend pattern for DRY code:
   - Base schema shares common fields (type, toolCallId, toolName, input, timestamp)
   - Pending variant: state="input-available", no output field
   - Available variant: state="output-available", output required

2. Remove dead ReasoningStartEventSchema:
   - Schema was defined but never emitted by backend
   - Not in WorkspaceChatMessageSchema union
   - No type guard existed for it

3. Update MuxToolPart type to use Zod inference:
   - Type now properly discriminates based on state
   - Accessing output requires narrowing to output-available state

refactor: simplify tool output redaction with type narrowing

Remove explicit DynamicToolPart cast in favor of TypeScript's
built-in type narrowing after the discriminant check. The type
guard `part.type !== "dynamic-tool"` already narrows the type,
making the cast redundant.

Also eliminate intermediate variables (toolPart, redacted) by
returning the new object directly, reducing visual noise.

fix: resolve race condition in queued messages test

Capture event count before interrupt to establish baseline, then
poll for new events rather than waiting for next event. The clear
event may arrive before or simultaneously with stream-abort, causing
the previous waitForQueuedMessageEvent call to miss it or timeout.

refactor: rename ORPC types and hooks to generic API naming

Rename ORPCClient to APIClient, useORPC to useAPI, and ORPCProvider
to APIProvider. Move the module from src/browser/orpc/react.tsx to
src/browser/hooks/useAPI.tsx to better reflect its purpose as a
general API client abstraction rather than being tied to the oRPC
implementation detail.

This decouples the public interface from the underlying transport
mechanism, making future backend changes transparent to consumers.

refactor: expose connection state from useAPI hook with discriminated union

Changed useAPI from returning just the client to returning a discriminated
union with connection state, enabling consumers to handle loading/error
states with skeleton loaders instead of blocking the entire UI.

Changes:
- useAPI now returns `{ api, status, error, authenticate, retry }`
- `api` is `APIClient | null` based on connection state (type-safe)
- `status` is one of: "connecting", "connected", "auth_required", "error"
- When `status === "connected"`, TypeScript knows `api` is non-null
- Auth modal moved to App.tsx (rendered after all hooks)
- Moved file from hooks/useAPI.tsx to contexts/API.tsx (follows codebase
  convention where Context+Provider+hook combinations live in contexts/)

Updated ~60 consumer files with null guards before API calls.

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

fix: add @babel/preset-react for JSX transpilation in Jest tests

fix: add missing timestamp field to ToolCallEndEvent schema and usages

fix: use ref for ORPCProvider cleanup to avoid stale closure

The useEffect cleanup captured state at mount time ('connecting'),
so even after transitioning to 'connected', cleanup never ran.
Now stores cleanup function in a ref that's always current.

test: add feature branch to storybook mock branch list

Extend listBranches mock response with a feature branch example
to better represent realistic branch listings during component
development and testing.

fix: batch async message yields to prevent scroll issues

The oRPC async generator was yielding messages one at a time with async
boundaries, causing premature React renders during history replay. This
led to scroll-to-bottom firing before all messages loaded.

Extract createAsyncMessageQueue utility that yields all queued messages
synchronously (no async pauses within a batch). Used by both the real
router and storybook mocks to match original IPC callback behavior.

fix: add missing type discriminators to storybook chat messages

The MarkdownTables story was emitting messages without the required
`type: "message"` field. The `as WorkspaceChatMessage` type casts
hid this from TypeScript, causing messages to not be recognized
by the chat processor and rendering "No Messages Yet" instead.

Also fix ChatEventProcessor tests that had invalid event shapes:
- Remove invalid `role`/`timestamp` from stream-start events
- Add missing `workspaceId`/`tokens` to delta events

fix: use useLayoutEffect for initial scroll to fix Chromatic snapshots

The scroll-to-bottom when workspace loads was using useEffect with
requestAnimationFrame, which runs asynchronously after browser paint.
Chromatic could capture the snapshot before scroll completed.

Switch to useLayoutEffect which runs synchronously after DOM mutations
but before paint, ensuring scroll happens before Chromatic captures.
This also removes the need for the RAF wrapper since useLayoutEffect
already guarantees DOM is ready.

fix: add play functions to ensure Chromatic captures scrolled state

- Add waitForChatScroll play function that waits for messages to load
  and scroll to complete before Chromatic takes screenshots
- Add data-testid="message-window" to scroll container in AIView
- Add data-testid="chat-message" to message wrappers for test queries
- Apply play function to ActiveWorkspaceWithChat and MarkdownTables stories
- Fix ProviderIcon lint error: remove redundant "mux-gateway" union type
  (already included in ProviderName)

fix: resolve React Native typecheck errors

- Add missing 'error' event handler in normalizeChatEvent.ts
  Converts error events to stream-error for mobile display
- Fix result.metadata access in WorkspaceScreen.tsx
  ResultSchema wraps data, so access result.data.metadata not result.metadata
- Add RequestInitWithDispatcher type in aiService.ts
  Extends RequestInit with undici-specific dispatcher property for Node.js

fix: use queueMicrotask instead of setTimeout in story mocks

Replace setTimeout(..., 100) with queueMicrotask() for message delivery
in Storybook mocks. This ensures messages arrive synchronously (in the
microtask queue) rather than 100ms later, eliminating timing races with
Chromatic's screenshot capture.

- All onChat mock callbacks now use queueMicrotask for message delivery
- Add chromatic: { delay: 500 } as backup for ActiveWorkspaceWithChat
  and MarkdownTables stories
- Fix import: use storybook/test instead of @storybook/test (Storybook 10)

fix: remove deprecated @storybook/addon-interactions from config

In Storybook 10, interaction testing is built into the core and the
addon-interactions package was deprecated. Remove it from the addons
list to fix build failures caused by version mismatch.

fix: add semver 7.x to fix storybook build in CI

Storybook 10 imports semver/functions/sort.js which only exists in
semver 7.x. The root-level semver was 6.x (needed by babel), causing
ESM resolution in Node 20.x to fail in CI.

Adding semver ^7.x as a direct dependency forces the root-level
version to 7.x, which is backwards compatible with 6.x consumers.

fix: add missing fields to oRPC provider and workspace schemas

The ProviderConfigInfoSchema was missing couponCodeSet (for Mux Gateway)
and aws (for Bedrock). oRPC strips fields not in the schema, so these
values were never reaching the frontend UI.

Also fixes workspace.fork to use FrontendWorkspaceMetadataSchema instead
of WorkspaceMetadataSchema, ensuring namedWorkspacePath is not stripped.

refactor: consolidate provider types to single source of truth

Eliminates triple-definition of ProviderConfigInfo/AWSCredentialStatus types
that existed in providerService.ts, Settings/types.ts, and the oRPC schema.
Now the Zod schema is the single source of truth, with TypeScript types
derived via z.infer.

Adds conformance tests that validate oRPC schemas preserve all fields when
parsing - this would have caught the missing couponCodeSet/aws fields bug.

refactor: improve tool part schema type safety and remove dead code

1. Refactor MuxToolPartSchema using extend pattern for DRY code:
   - Base schema shares common fields (type, toolCallId, toolName, input, timestamp)
   - Pending variant: state="input-available", no output field
   - Available variant: state="output-available", output required

2. Remove dead ReasoningStartEventSchema:
   - Schema was defined but never emitted by backend
   - Not in WorkspaceChatMessageSchema union
   - No type guard existed for it

3. Update MuxToolPart type to use Zod inference:
   - Type now properly discriminates based on state
   - Accessing output requires narrowing to output-available state

refactor: simplify tool output redaction with type narrowing

Remove explicit DynamicToolPart cast in favor of TypeScript's
built-in type narrowing after the discriminant check. The type
guard `part.type !== "dynamic-tool"` already narrows the type,
making the cast redundant.

Also eliminate intermediate variables (toolPart, redacted) by
returning the new object directly, reducing visual noise.

fix: resolve race condition in queued messages test

Capture event count before interrupt to establish baseline, then
poll for new events rather than waiting for next event. The clear
event may arrive before or simultaneously with stream-abort, causing
the previous waitForQueuedMessageEvent call to miss it or timeout.

refactor: rename ORPC types and hooks to generic API naming

Rename ORPCClient to APIClient, useORPC to useAPI, and ORPCProvider
to APIProvider. Move the module from src/browser/orpc/react.tsx to
src/browser/hooks/useAPI.tsx to better reflect its purpose as a
general API client abstraction rather than being tied to the oRPC
implementation detail.

This decouples the public interface from the underlying transport
mechanism, making future backend changes transparent to consumers.

refactor: expose connection state from useAPI hook with discriminated union

Changed useAPI from returning just the client to returning a discriminated
union with connection state, enabling consumers to handle loading/error
states with skeleton loaders instead of blocking the entire UI.

Changes:
- useAPI now returns `{ api, status, error, authenticate, retry }`
- `api` is `APIClient | null` based on connection state (type-safe)
- `status` is one of: "connecting", "connected", "auth_required", "error"
- When `status === "connected"`, TypeScript knows `api` is non-null
- Auth modal moved to App.tsx (rendered after all hooks)
- Moved file from hooks/useAPI.tsx to contexts/API.tsx (follows codebase
  convention where Context+Provider+hook combinations live in contexts/)

Updated ~60 consumer files with null guards before API calls.

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

fix: add @babel/preset-react for JSX transpilation in Jest tests

fix: add missing timestamp field to ToolCallEndEvent schema and usages

fix: use ref for ORPCProvider cleanup to avoid stale closure

The useEffect cleanup captured state at mount time ('connecting'),
so even after transitioning to 'connected', cleanup never ran.
Now stores cleanup function in a ref that's always current.

test: add feature branch to storybook mock branch list

Extend listBranches mock response with a feature branch example
to better represent realistic branch listings during component
development and testing.

fix: batch async message yields to prevent scroll issues

The oRPC async generator was yielding messages one at a time with async
boundaries, causing premature React renders during history replay. This
led to scroll-to-bottom firing before all messages loaded.

Extract createAsyncMessageQueue utility that yields all queued messages
synchronously (no async pauses within a batch). Used by both the real
router and storybook mocks to match original IPC callback behavior.

fix: add missing type discriminators to storybook chat messages

The MarkdownTables story was emitting messages without the required
`type: "message"` field. The `as WorkspaceChatMessage` type casts
hid this from TypeScript, causing messages to not be recognized
by the chat processor and rendering "No Messages Yet" instead.

Also fix ChatEventProcessor tests that had invalid event shapes:
- Remove invalid `role`/`timestamp` from stream-start events
- Add missing `workspaceId`/`tokens` to delta events

fix: use useLayoutEffect for initial scroll to fix Chromatic snapshots

The scroll-to-bottom when workspace loads was using useEffect with
requestAnimationFrame, which runs asynchronously after browser paint.
Chromatic could capture the snapshot before scroll completed.

Switch to useLayoutEffect which runs synchronously after DOM mutations
but before paint, ensuring scroll happens before Chromatic captures.
This also removes the need for the RAF wrapper since useLayoutEffect
already guarantees DOM is ready.

fix: add play functions to ensure Chromatic captures scrolled state

- Add waitForChatScroll play function that waits for messages to load
  and scroll to complete before Chromatic takes screenshots
- Add data-testid="message-window" to scroll container in AIView
- Add data-testid="chat-message" to message wrappers for test queries
- Apply play function to ActiveWorkspaceWithChat and MarkdownTables stories
- Fix ProviderIcon lint error: remove redundant "mux-gateway" union type
  (already included in ProviderName)

fix: resolve React Native typecheck errors

- Add missing 'error' event handler in normalizeChatEvent.ts
  Converts error events to stream-error for mobile display
- Fix result.metadata access in WorkspaceScreen.tsx
  ResultSchema wraps data, so access result.data.metadata not result.metadata
- Add RequestInitWithDispatcher type in aiService.ts
  Extends RequestInit with undici-specific dispatcher property for Node.js

fix: use queueMicrotask instead of setTimeout in story mocks

Replace setTimeout(..., 100) with queueMicrotask() for message delivery
in Storybook mocks. This ensures messages arrive synchronously (in the
microtask queue) rather than 100ms later, eliminating timing races with
Chromatic's screenshot capture.

- All onChat mock callbacks now use queueMicrotask for message delivery
- Add chromatic: { delay: 500 } as backup for ActiveWorkspaceWithChat
  and MarkdownTables stories
- Fix import: use storybook/test instead of @storybook/test (Storybook 10)

fix: remove deprecated @storybook/addon-interactions from config

In Storybook 10, interaction testing is built into the core and the
addon-interactions package was deprecated. Remove it from the addons
list to fix build failures caused by version mismatch.

fix: add semver 7.x to fix storybook build in CI

Storybook 10 imports semver/functions/sort.js which only exists in
semver 7.x. The root-level semver was 6.x (needed by babel), causing
ESM resolution in Node 20.x to fail in CI.

Adding semver ^7.x as a direct dependency forces the root-level
version to 7.x, which is backwards compatible with 6.x consumers.

fix: add missing fields to oRPC provider and workspace schemas

The ProviderConfigInfoSchema was missing couponCodeSet (for Mux Gateway)
and aws (for Bedrock). oRPC strips fields not in the schema, so these
values were never reaching the frontend UI.

Also fixes workspace.fork to use FrontendWorkspaceMetadataSchema instead
of WorkspaceMetadataSchema, ensuring namedWorkspacePath is not stripped.

refactor: consolidate provider types to single source of truth

Eliminates triple-definition of ProviderConfigInfo/AWSCredentialStatus types
that existed in providerService.ts, Settings/types.ts, and the oRPC schema.
Now the Zod schema is the single source of truth, with TypeScript types
derived via z.infer.

Adds conformance tests that validate oRPC schemas preserve all fields when
parsing - this would have caught the missing couponCodeSet/aws fields bug.

refactor: improve tool part schema type safety and remove dead code

1. Refactor MuxToolPartSchema using extend pattern for DRY code:
   - Base schema shares common fields (type, toolCallId, toolName, input, timestamp)
   - Pending variant: state="input-available", no output field
   - Available variant: state="output-available", output required

2. Remove dead ReasoningStartEventSchema:
   - Schema was defined but never emitted by backend
   - Not in WorkspaceChatMessageSchema union
   - No type guard existed for it

3. Update MuxToolPart type to use Zod inference:
   - Type now properly discriminates based on state
   - Accessing output requires narrowing to output-available state

refactor: simplify tool output redaction with type narrowing

Remove explicit DynamicToolPart cast in favor of TypeScript's
built-in type narrowing after the discriminant check. The type
guard `part.type !== "dynamic-tool"` already narrows the type,
making the cast redundant.

Also eliminate intermediate variables (toolPart, redacted) by
returning the new object directly, reducing visual noise.

fix: resolve race condition in queued messages test

Capture event count before interrupt to establish baseline, then
poll for new events rather than waiting for next event. The clear
event may arrive before or simultaneously with stream-abort, causing
the previous waitForQueuedMessageEvent call to miss it or timeout.

refactor: rename ORPC types and hooks to generic API naming

Rename ORPCClient to APIClient, useORPC to useAPI, and ORPCProvider
to APIProvider. Move the module from src/browser/orpc/react.tsx to
src/browser/hooks/useAPI.tsx to better reflect its purpose as a
general API client abstraction rather than being tied to the oRPC
implementation detail.

This decouples the public interface from the underlying transport
mechanism, making future backend changes transparent to consumers.

refactor: expose connection state from useAPI hook with discriminated union

Changed useAPI from returning just the client to returning a discriminated
union with connection state, enabling consumers to handle loading/error
states with skeleton loaders instead of blocking the entire UI.

Changes:
- useAPI now returns `{ api, status, error, authenticate, retry }`
- `api` is `APIClient | null` based on connection state (type-safe)
- `status` is one of: "connecting", "connected", "auth_required", "error"
- When `status === "connected"`, TypeScript knows `api` is non-null
- Auth modal moved to App.tsx (rendered after all hooks)
- Moved file from hooks/useAPI.tsx to contexts/API.tsx (follows codebase
  convention where Context+Provider+hook combinations live in contexts/)

Updated ~60 consumer files with null guards before API calls.

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

fix: add @babel/preset-react for JSX transpilation in Jest tests

fix: add missing timestamp field to ToolCallEndEvent schema and usages

fix: use ref for ORPCProvider cleanup to avoid stale closure

The useEffect cleanup captured state at mount time ('connecting'),
so even after transitioning to 'connected', cleanup never ran.
Now stores cleanup function in a ref that's always current.

test: add feature branch to storybook mock branch list

Extend listBranches mock response with a feature branch example
to better represent realistic branch listings during component
development and testing.

fix: batch async message yields to prevent scroll issues

The oRPC async generator was yielding messages one at a time with async
boundaries, causing premature React renders during history replay. This
led to scroll-to-bottom firing before all messages loaded.

Extract createAsyncMessageQueue utility that yields all queued messages
synchronously (no async pauses within a batch). Used by both the real
router and storybook mocks to match original IPC callback behavior.

fix: add missing type discriminators to storybook chat messages

The MarkdownTables story was emitting messages without the required
`type: "message"` field. The `as WorkspaceChatMessage` type casts
hid this from TypeScript, causing messages to not be recognized
by the chat processor and rendering "No Messages Yet" instead.

Also fix ChatEventProcessor tests that had invalid event shapes:
- Remove invalid `role`/`timestamp` from stream-start events
- Add missing `workspaceId`/`tokens` to delta events

fix: use useLayoutEffect for initial scroll to fix Chromatic snapshots

The scroll-to-bottom when workspace loads was using useEffect with
requestAnimationFrame, which runs asynchronously after browser paint.
Chromatic could capture the snapshot before scroll completed.

Switch to useLayoutEffect which runs synchronously after DOM mutations
but before paint, ensuring scroll happens before Chromatic captures.
This also removes the need for the RAF wrapper since useLayoutEffect
already guarantees DOM is ready.

fix: add play functions to ensure Chromatic captures scrolled state

- Add waitForChatScroll play function that waits for messages to load
  and scroll to complete before Chromatic takes screenshots
- Add data-testid="message-window" to scroll container in AIView
- Add data-testid="chat-message" to message wrappers for test queries
- Apply play function to ActiveWorkspaceWithChat and MarkdownTables stories
- Fix ProviderIcon lint error: remove redundant "mux-gateway" union type
  (already included in ProviderName)

fix: resolve React Native typecheck errors

- Add missing 'error' event handler in normalizeChatEvent.ts
  Converts error events to stream-error for mobile display
- Fix result.metadata access in WorkspaceScreen.tsx
  ResultSchema wraps data, so access result.data.metadata not result.metadata
- Add RequestInitWithDispatcher type in aiService.ts
  Extends RequestInit with undici-specific dispatcher property for Node.js

fix: use queueMicrotask instead of setTimeout in story mocks

Replace setTimeout(..., 100) with queueMicrotask() for message delivery
in Storybook mocks. This ensures messages arrive synchronously (in the
microtask queue) rather than 100ms later, eliminating timing races with
Chromatic's screenshot capture.

- All onChat mock callbacks now use queueMicrotask for message delivery
- Add chromatic: { delay: 500 } as backup for ActiveWorkspaceWithChat
  and MarkdownTables stories
- Fix import: use storybook/test instead of @storybook/test (Storybook 10)

fix: remove deprecated @storybook/addon-interactions from config

In Storybook 10, interaction testing is built into the core and the
addon-interactions package was deprecated. Remove it from the addons
list to fix build failures caused by version mismatch.

fix: add semver 7.x to fix storybook build in CI

Storybook 10 imports semver/functions/sort.js which only exists in
semver 7.x. The root-level semver was 6.x (needed by babel), causing
ESM resolution in Node 20.x to fail in CI.

Adding semver ^7.x as a direct dependency forces the root-level
version to 7.x, which is backwards compatible with 6.x consumers.

fix: add missing fields to oRPC provider and workspace schemas

The ProviderConfigInfoSchema was missing couponCodeSet (for Mux Gateway)
and aws (for Bedrock). oRPC strips fields not in the schema, so these
values were never reaching the frontend UI.

Also fixes workspace.fork to use FrontendWorkspaceMetadataSchema instead
of WorkspaceMetadataSchema, ensuring namedWorkspacePath is not stripped.

refactor: consolidate provider types to single source of truth

Eliminates triple-definition of ProviderConfigInfo/AWSCredentialStatus types
that existed in providerService.ts, Settings/types.ts, and the oRPC schema.
Now the Zod schema is the single source of truth, with TypeScript types
derived via z.infer.

Adds conformance tests that validate oRPC schemas preserve all fields when
parsing - this would have caught the missing couponCodeSet/aws fields bug.

refactor: improve tool part schema type safety and remove dead code

1. Refactor MuxToolPartSchema using extend pattern for DRY code:
   - Base schema shares common fields (type, toolCallId, toolName, input, timestamp)
   - Pending variant: state="input-available", no output field
   - Available variant: state="output-available", output required

2. Remove dead ReasoningStartEventSchema:
   - Schema was defined but never emitted by backend
   - Not in WorkspaceChatMessageSchema union
   - No type guard existed for it

3. Update MuxToolPart type to use Zod inference:
   - Type now properly discriminates based on state
   - Accessing output requires narrowing to output-available state

refactor: simplify tool output redaction with type narrowing

Remove explicit DynamicToolPart cast in favor of TypeScript's
built-in type narrowing after the discriminant check. The type
guard `part.type !== "dynamic-tool"` already narrows the type,
making the cast redundant.

Also eliminate intermediate variables (toolPart, redacted) by
returning the new object directly, reducing visual noise.

fix: resolve race condition in queued messages test

Capture event count before interrupt to establish baseline, then
poll for new events rather than waiting for next event. The clear
event may arrive before or simultaneously with stream-abort, causing
the previous waitForQueuedMessageEvent call to miss it or timeout.

refactor: rename ORPC types and hooks to generic API naming

Rename ORPCClient to APIClient, useORPC to useAPI, and ORPCProvider
to APIProvider. Move the module from src/browser/orpc/react.tsx to
src/browser/hooks/useAPI.tsx to better reflect its purpose as a
general API client abstraction rather than being tied to the oRPC
implementation detail.

This decouples the public interface from the underlying transport
mechanism, making future backend changes transparent to consumers.

refactor: expose connection state from useAPI hook with discriminated union

Changed useAPI from returning just the client to returning a discriminated
union with connection state, enabling consumers to handle loading/error
states with skeleton loaders instead of blocking the entire UI.

Changes:
- useAPI now returns `{ api, status, error, authenticate, retry }`
- `api` is `APIClient | null` based on connection state (type-safe)
- `status` is one of: "connecting", "connected", "auth_required", "error"
- When `status === "connected"`, TypeScript knows `api` is non-null
- Auth modal moved to App.tsx (rendered after all hooks)
- Moved file from hooks/useAPI.tsx to contexts/API.tsx (follows codebase
  convention where Context+Provider+hook combinations live in contexts/)

Updated ~60 consumer files with null guards before API calls.

This commit reintroduces the ORPC refactoring that was originally merged
in #763 and subsequently reverted in #777 due to regressions.

## Original PR: #763
Replaces the custom IPC layer with oRPC for type-safe RPC between
browser/renderer and backend processes.

## Why it was reverted (#777)
The original migration caused regressions including:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output
- Auto-compaction trigger deletion

## What's different this time
- Rebased onto latest main which includes fixes that were developed
  post-revert (model favorites, auto-compaction, etc.)
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- New ORPC router (src/node/orpc/router.ts) - Central router with Zod schemas
- Schema definitions (src/common/orpc/schemas.ts) - Shared validation
- ServiceContainer (src/node/services/serviceContainer.ts) - DI container
- React integration (src/browser/orpc/react.tsx) - ORPCProvider and useORPC()

### Transport
- Desktop (Electron): MessagePort-based RPC via @orpc/server/message-port
- Server mode: HTTP + WebSocket via @orpc/server/node and @orpc/server/ws
- Auth middleware with timing-safe token comparison

### Removed
- src/browser/api.ts (old HTTP/WS client)
- src/node/services/ipcMain.ts (old IPC handler registration)
- Old IPC method definitions in preload.ts

---
_Generated with mux_

fix: add @babel/preset-react for JSX transpilation in Jest tests

fix: add missing timestamp field to ToolCallEndEvent schema and usages

fix: use ref for ORPCProvider cleanup to avoid stale closure

The useEffect cleanup captured state at mount time ('connecting'),
so even after transitioning to 'connected', cleanup never ran.
Now stores cleanup function in a ref that's always current.

test: add feature branch to storybook mock branch list

Extend listBranches mock response with a feature branch example
to better represent realistic branch listings during component
development and testing.

fix: batch async message yields to prevent scroll issues

The oRPC async generator was yielding messages one at a time with async
boundaries, causing premature React renders during history replay. This
led to scroll-to-bottom firing before all messages loaded.

Extract createAsyncMessageQueue utility that yields all queued messages
synchronously (no async pauses within a batch). Used by both the real
router and storybook mocks to match original IPC callback behavior.

fix: add missing type discriminators to storybook chat messages

The MarkdownTables story was emitting messages without the required
`type: "message"` field. The `as WorkspaceChatMessage` type casts
hid this from TypeScript, causing messages to not be recognized
by the chat processor and rendering "No Messages Yet" instead.

Also fix ChatEventProcessor tests that had invalid event shapes:
- Remove invalid `role`/`timestamp` from stream-start events
- Add missing `workspaceId`/`tokens` to delta events

fix: use useLayoutEffect for initial scroll to fix Chromatic snapshots

The scroll-to-bottom when workspace loads was using useEffect with
requestAnimationFrame, which runs asynchronously after browser paint.
Chromatic could capture the snapshot before scroll completed.

Switch to useLayoutEffect which runs synchronously after DOM mutations
but before paint, ensuring scroll happens before Chromatic captures.
This also removes the need for the RAF wrapper since useLayoutEffect
already guarantees DOM is ready.

fix: add play functions to ensure Chromatic captures scrolled state

- Add waitForChatScroll play function that waits for messages to load
  and scroll to complete before Chromatic takes screenshots
- Add data-testid="message-window" to scroll container in AIView
- Add data-testid="chat-message" to message wrappers for test queries
- Apply play function to ActiveWorkspaceWithChat and MarkdownTables stories
- Fix ProviderIcon lint error: remove redundant "mux-gateway" union type
  (already included in ProviderName)

fix: resolve React Native typecheck errors

- Add missing 'error' event handler in normalizeChatEvent.ts
  Converts error events to stream-error for mobile display
- Fix result.metadata access in WorkspaceScreen.tsx
  ResultSchema wraps data, so access result.data.metadata not result.metadata
- Add RequestInitWithDispatcher type in aiService.ts
  Extends RequestInit with undici-specific dispatcher property for Node.js

fix: use queueMicrotask instead of setTimeout in story mocks

Replace setTimeout(..., 100) with queueMicrotask() for message delivery
in Storybook mocks. This ensures messages arrive synchronously (in the
microtask queue) rather than 100ms later, eliminating timing races with
Chromatic's screenshot capture.

- All onChat mock callbacks now use queueMicrotask for message delivery
- Add chromatic: { delay: 500 } as backup for ActiveWorkspaceWithChat
  and MarkdownTables stories
- Fix import: use storybook/test instead of @storybook/test (Storybook 10)

fix: remove deprecated @storybook/addon-interactions from config

In Storybook 10, interaction testing is built into the core and the
addon-interactions package was deprecated. Remove it from the addons
list to fix build failures caused by version mismatch.

fix: add semver 7.x to fix storybook build in CI

Storybook 10 imports semver/functions/sort.js which only exists in
semver 7.x. The root-level semver was 6.x (needed by babel), causing
ESM resolution in Node 20.x to fail in CI.

Adding semver ^7.x as a direct dependency forces the root-level
version to 7.x, which is backwards compatible with 6.x consumers.

fix: add missing fields to oRPC provider and workspace schemas

The ProviderConfigInfoSchema was missing couponCodeSet (for Mux Gateway)
and aws (for Bedrock). oRPC strips fields not in the schema, so these
values were never reaching the frontend UI.

Also fixes workspace.fork to use FrontendWorkspaceMetadataSchema instead
of WorkspaceMetadataSchema, ensuring namedWorkspacePath is not stripped.

refactor: consolidate provider types to single source of truth

Eliminates triple-definition of ProviderConfigInfo/AWSCredentialStatus types
that existed in providerService.ts, Settings/types.ts, and the oRPC schema.
Now the Zod schema is the single source of truth, with TypeScript types
derived via z.infer.

Adds conformance tests that validate oRPC schemas preserve all fields when
parsing - this would have caught the missing couponCodeSet/aws fields bug.

refactor: improve tool part schema type safety and remove dead code

1. Refactor MuxToolPartSchema using extend pattern for DRY code:
   - Base schema shares common fields (type, toolCallId, toolName, input, timestamp)
   - Pending variant: state="input-available", no output field
   - Available variant: state="output-available", output required

2. Remove dead ReasoningStartEventSchema:
   - Schema was defined but never emitted by backend
   - Not in WorkspaceChatMessageSchema union
   - No type guard existed for it

3. Update MuxToolPart type to use Zod inference:
   - Type now properly discriminates based on state
   - Accessing output requires narrowing to output-available state

refactor: simplify tool output redaction with type narrowing

Remove explicit DynamicToolPart cast in favor of TypeScript's
built-in type narrowing after the discriminant check. The type
guard `part.type !== "dynamic-tool"` already narrows the type,
making the cast redundant.

Also eliminate intermediate variables (toolPart, redacted) by
returning the new object directly, reducing visual noise.

fix: resolve race condition in queued messages test

Capture event count before interrupt to establish baseline, then
poll for new events rather than waiting for next event. The clear
event may arrive before or simultaneously with stream-abort, causing
the previous waitForQueuedMessageEvent call to miss it or timeout.

refactor: rename ORPC types and hooks to generic API naming

Rename ORPCClient to APIClient, useORPC to useAPI, and ORPCProvider
to APIProvider. Move the module from src/browser/orpc/react.tsx to
src/browser/hooks/useAPI.tsx to better reflect its purpose as a
general API client abstraction rather than being tied to the oRPC
implementation detail.

This decouples the public interface from the underlying transport
mechanism, making future backend changes transparent to consumers.

refactor: expose connection state from useAPI hook with discriminated union

Changed useAPI from returning just the client to returning a discriminated
union with connection state, enabling consumers to handle loading/error
states with skeleton loaders instead of blocking the entire UI.

Changes:
- useAPI now returns `{ api, status, error, authenticate, retry }`
- `api` is `APIClient | null` based on connection state (type-safe)
- `status` is one of: "connecting", "connected", "auth_required", "error"
- When `status === "connected"`, TypeScript knows `api` is non-null
- Auth modal moved to App.tsx (rendered after all hooks)
- Moved file from hooks/useAPI.tsx to contexts/API.tsx (follows codebase
  convention where Context+Provider+hook combinations live in contexts/)

Updated ~60 consumer files with null guards before API calls.

## Summary

Reintroduces the ORPC refactoring originally merged in #763 and reverted
in #777.

This replaces the custom IPC layer with [oRPC](https://orpc.unnoq.com/)
for type-safe RPC between browser/renderer and backend processes.

## Why it was reverted (#777)

The original migration caused regressions:
- Streaming content delay from ORPC schema validation
- Field stripping issues in sendMessage output  
- Auto-compaction trigger deletion

## What's different this time

- Rebased onto latest main which includes fixes developed post-revert
- Conflict resolution preserves upstream features added after revert:
  - Workspace name collision retry with hash suffix (#779)
  - Mux Gateway coupon code handling with default models
  - AWS Bedrock credential nested structure

## Key Changes

### Architecture
- **New ORPC router** (`src/node/orpc/router.ts`) - Central router with
Zod schemas
- **Schema definitions** (`src/common/orpc/schemas.ts`) - Shared
validation
- **ServiceContainer** (`src/node/services/serviceContainer.ts`) - DI
container
- **React integration** (`src/browser/orpc/react.tsx`) - `ORPCProvider`
and `useORPC()`

### Transport
- **Desktop (Electron)**: MessagePort-based RPC via
`@orpc/server/message-port`
- **Server mode**: HTTP + WebSocket via `@orpc/server/node` and
`@orpc/server/ws`
- Auth middleware with timing-safe token comparison

### Removed
- `src/browser/api.ts` (old HTTP/WS client)
- `src/node/services/ipcMain.ts` (old IPC handler registration)
- Old IPC method definitions in preload.ts

## Test plan

- [x] Run `make typecheck` - passes locally
- [x] Run `make test` - verify existing tests pass
- [x] Manual testing of desktop app (Electron)
- [x] Manual testing of server mode (browser)
- [x] Verify streaming chat works without delays
- [x] Verify auto-compaction triggers correctly

---
_Generated with [mux](https://github.com/coder/mux)_